Efficient algorithm to eliminate redundant specific prefixes in forwarding information base using trie

ABSTRACT

A network element and method for programming a network element that includes detecting an update to a first route in a routing information base (RIB) is disclosed. The method includes locating a first route network prefix associated with the first route within a network prefix trie (NPT); determining that, prior to the update, a first parent network prefix and the first route network prefix were reachable using a pair of different next hops connected to the network element; and determining that, after the update, the first parent network prefix and the first route network prefix are reachable using a first common next hop connected to the network element. The method also includes removing an existing forwarding information base (FIB) entry in the FIB associated with the first route network prefix.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of U.S. patentapplication Ser. No. 15/470,417, filed on Mar. 27, 2017, now U.S. Pat.No. 10,892,986, and entitled: “EFFICIENT ALGORITHM TO ELIMINATEREDUNDANT SPECIFIC PREFIXES IN FORWARDING INFORMATION BASE USING TRIE”.Accordingly, this application claims benefit of U.S. patent applicationSer. No. 15/470,417 under 35 U.S.C. § 120. U.S. patent application Ser.No. 15/470,417 is hereby incorporated by reference in their entirety.

BACKGROUND

Modern network elements include switch chips capable of storingthousands of routes (each associated with a network prefix) in a localrouting table. With these immense routing tables, there is a possibilitythat some more-specific routes may be a subset of other less-specificroutes, leading to unnecessary redundancy in information. In waiving theprogramming of the more-specific routes, which may be subsumed by theless-specific routes, memory and/or persistent storage on a networkelement may be saved.

SUMMARY

In general, in one aspect, the invention relates to a method forprogramming a network element. The method includes detecting an additionof a first route in a routing information base (RIB) on the networkelement, adding, in response to detecting the addition, a first routenetwork prefix associated with the first route to a network prefix trie(NPT), identifying, based on the adding, a first parent network prefixfor the first route network prefix using the NPT, making a firstdetermination that the first route network prefix and the first parentnetwork prefix are reachable via a first common next hop connected tothe network element, and waiving, based on the first determination, acreation of a forwarding information base (FIB) entry associated withthe first route network prefix in a FIB on the network element.

In general, in one aspect, the invention relates to a network element.The network element includes a data plane including a forwardinginformation base (FIB), and a control plane including a routinginformation base (RIB) and a FIB Compressor operatively connected to theRIB and the FIB, and configured to detect an addition of a first routein RIB, add, in response to detecting the addition, a first routenetwork prefix associated with the first route to a network prefix trie(NPT), identify, based on the adding, a first parent network prefix forthe first route network prefix using the NPT, make a first determinationthat the first route network prefix and the first parent network prefixare reachable via a first common next hop connected to the networkelement, and waive, based on the first determination, a creation of aFIB entry associated with the first route network prefix in the FIB.

In general, in one aspect, the invention relates to a non-transitorycomputer readable medium (CRM) including computer readable program code,which when executed by a computer processor, enables the computerprocessor to detect an addition of a first route in a routinginformation base (RIB) on a network element, add, in response todetecting the addition, a first route network prefix associated with thefirst route to a network prefix trie (NPT), identify, based on theadding, a first parent network prefix for the first route network prefixusing the NPT, make a first determination that the first route networkprefix and the first parent network prefix are reachable using a firstcommon next hop connected to the network element, and waive, based onthe first determination, a creation of a forwarding information base(FIB) entry associated with the first route network prefix in a FIB onthe network element.

Other aspects of the invention will be apparent from the followingdescription and the appended claims.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 shows a system in accordance with one or more embodiments of theinvention.

FIG. 2 shows a network element in accordance with one or moreembodiments of the invention.

FIG. 3A shows a routing information base in accordance with one or moreembodiments of the invention.

FIG. 3B shows a forwarding information base in accordance with one ormore embodiments of the invention.

FIG. 3C shows a forwarding equivalence class table in accordance withone or more embodiments of the invention.

FIG. 3D shows an example network prefix trie in accordance with one ormore embodiments of the invention.

FIG. 3E shows trie nodal information in accordance with one or moreembodiments of the invention.

FIGS. 4A-4D show flowcharts describing a method for adding a networkprefix to a network prefix trie in accordance with one or moreembodiments of the invention.

FIGS. 5A-5D show flowcharts describing a method for deleting a networkprefix from a network prefix trie in accordance with one or moreembodiments of the invention.

FIGS. 6A-6F show flowcharts describing a method for updating a networkprefix in a network prefix trie in accordance with one or moreembodiments of the invention.

FIGS. 7A-7D show various aspects of an example in accordance with one ormore embodiments of the invention.

FIGS. 8A and 8B show computing systems in accordance with one or moreembodiments of the invention.

DETAILED DESCRIPTION

Specific embodiments of the invention will now be described in detailwith reference to the accompanying figures. In the following detaileddescription of the embodiments of the invention, numerous specificdetails are set forth in order to provide a more thorough understandingof the invention. However, it will be apparent to one of ordinary skillin the art that the invention may be practiced without these specificdetails. In other instances, well-known features have not been describedin detail to avoid unnecessarily complicating the description.

In the following description of FIGS. 1-8B, any component described withregard to a figure, in various embodiments of the invention, may beequivalent to one or more like-named components described with regard toany other figure. For brevity, descriptions of these components will notbe repeated with regard to each figure. Thus, each and every embodimentof the components of each figure is incorporated by reference andassumed to be optionally present within every other figure having one ormore like-named components. Additionally, in accordance with variousembodiments of the invention, any description of the components of afigure is to be interpreted as an optional embodiment which may beimplemented in addition to, in conjunction with, or in place of theembodiments described with regard to a corresponding like-namedcomponent in any other figure.

Throughout the application, ordinal numbers (e.g., first, second, third,etc.) may be used as an adjective for an element (i.e., any noun in theapplication). The use of ordinal numbers is not to necessarily imply orcreate any particular ordering of the elements nor to limit any elementto being only a single element unless expressly disclosed, such as bythe use of the terms “before”, “after”, “single”, and other suchterminology. Rather, the use of ordinal numbers is to distinguishbetween the elements. By way of an example, a first element is distinctfrom a second element, and the first element may encompass more than oneelement and succeed (or precede) the second element in an ordering ofelements.

In general, embodiments of the invention relate to the compression of aforwarding information base (FIB) on a network element. Specifically,one or more embodiments of the invention entails maintaining ahierarchical trie data structure for cataloging all the network prefixesspecified in the routing information base (RIB) on the network element.More specifically, updates to the RIB are reflected onto a networkprefix trie (NPT) (e.g., the hierarchical trie data structure). Theupdates may correspond to an addition or a deletion of, or a change to,a route in the RIB, which prompts the addition or deletion of, or achange pertinent to, a network prefix associated with the route in theNPT. Further, based on the NPT and/or trie nodal information associatedwith each network prefix in the NPT, a parent and zero or more childnetwork prefixes relating to the route network prefix may be identified.Subsequently, updates to the FIB (including compression) are performedpending comparisons between bridging next hop information (BNHI) (fornext hops connected to the network element) corresponding to the routenetwork prefix, the parent network prefix, and the zero or more childnetwork prefixes.

One or more embodiments of the invention provide a method and system toimprove the efficiency for programming routes in a FIB. Morespecifically, an in-memory tree data structure is used to make a smallnumber of comparisons in order to: (i) determine whether to include theroute in the FIB and (ii) to determine whether, in response to adding anew route to the FIB, one or more existing entries in the FIB need to beremoved. Embodiments of the invention, enable the system to utilize asingle comparison between the route network prefix and a parent networkprefix in the tree data structure. If this comparison is successful(i.e., the route network prefix should be programmed into the FIB), thenthe route network prefix is compared to the immediate child networkprefixes of the parent network prefix in order to determine whether anyentries corresponding to the child network prefixes should be removed bythe FIB. In this manner, embodiments of the invention provide theability to efficiently program the FIB while reducing the maintaining ofredundant route network prefixes into the FIB.

FIG. 1 shows a system in accordance with one or more embodiments of theinvention. The system (100) includes a source device (102), one or morenetwork elements (104A-104N), and a destination device (106). Each ofthese components is described below.

In one embodiment of the invention, the aforementioned components may bedirectly or indirectly connected to each other using any combination ofwired and/or wireless connections. Further, the aforementionedcomponents may communicate with each other using any combination ofwired and/or wireless communication protocols.

In one embodiment of the invention, the source device (102) may be anycomputing system (see e.g., FIGS. 8A and 8B) that includes functionalityto communicate with the destination device (106). More specifically, thesource device (102) may include functionality to generate and transmitnetwork packets addressed to the destination device (106). The sourcedevice (102) may include further functionality to receive and processnetwork packets addressed to the source device (102) from thedestination device (106). Examples of the source device (102) include,but are not limited to, a desktop computer, a laptop computer, a tabletcomputer, a server, a smartphone, a virtual machine executing on any ofthe aforementioned examples, or any combination thereof.

In one embodiment of the invention, a network element (104A-104N) may bea physical device that includes persistent storage, memory (e.g., randomaccess memory (RAM), shared memory), one or more computer processor(s)(e.g., integrated circuits) (including a switch chip or networkprocessor)), and two or more physical network interfaces or ports. Thepersistent storage in the network element (104A-104N) may include anytype of non-transitory computer readable medium that includesinstructions, which when executed by the one or more computerprocessor(s), enable the network element (104A-104N) to performfunctions described below in accordance with one or more embodiments ofthe invention (see e.g., FIGS. 4A-6F). In one embodiment of theinvention, the various data structures pertinent to embodiments of theinvention (e.g., the routing information base (RIB), the forwardinginformation base (FIB), the forwarding equivalence class (FEC) Table,and the network prefix trie (NPT)) may be stored/maintained in thepersistent storage, the memory, any other storage mechanism, or anycombination thereof.

In one embodiment of the invention, a network element (104A-104N) mayinclude functionality to receive network packets at a network interfaceor port from the source device (102) or another (i.e., a second) networkelement (104A-104N). A network element (104A-104N) may include furtherfunctionality to subsequently transmit the received network packets toyet another (i.e., a third) network element or the destination device(106) through the same or a different network interface or port.Examples of a network element (104A-104N) include, but are not limitedto, a switch, a router, and a multilayer switch. A network element(104A-104N) is discussed in further detail below with respect to FIG. 2.

In one embodiment of the invention, the destination device (106) may beany computing system (see e.g., FIGS. 8A and 8B) that includesfunctionality to communicate with the source device (102). Morespecifically, the destination device (106) may include functionality toreceive and process network packets addressed to the destination device(106) from the source device (102). The destination device (106) mayinclude further functionality to generate and transmit other networkpackets addressed to the source device (102) in response to receivingnetwork packets from the source device (102). Examples of a destinationdevice (106) include, but are not limited to, a desktop computer, alaptop computer, a tablet computer, a server, a smartphone, a virtualmachine executing on any of the aforementioned examples, or acombination thereof.

While FIG. 1 shows a configuration of components, system configurationsother than that shown in FIG. 1 may be used without departing from thescope of the invention. For example, multiple destination devices and/ormultiple source devices may exist.

FIG. 2 shows a network element in accordance with one or moreembodiments of the invention. The network element (200A) includes acontrol plane (202) and a data plane (204). Each of these components isdescribed below.

In one embodiment of the invention, the control plane (202) may be afirst portion of the architecture employed in the network element(200A). The control plane (202) may be implemented using hardware,software, firmware, and/or any combination thereof. In one embodiment ofthe invention, the control plane (202) may include functionality tomanage the overall operation of the data plane (204) (includingprogramming of the FIB (210) and FEC table (212)). The control plane(202) includes a routing information base (RIB) (206) and a FIBCompressor (208). Each of these components is described below.

In one embodiment of the invention, the RIB (206) may be a datarepository for storing and tracking routes to network destinationsreachable from the network element (200A). As a data repository, the RIB(206) may take the form of any type of storage unit and/or device suchas, for example, a file system, a database, a collection of tables, orany other storage medium. Further, the RIB (206) may include multipledifferent storage units and/or devices. In one embodiment of theinvention, the RIB (206) may include information pertaining to thetopology of network immediately around the network element (200A). TheRIB (206) may be programmed through the selection of best paths orroutes for network packets by one or more routing protocols (e.g.,border gateway protocol (BGP), open shortest path first (OSPF), etc.)executing/employed on the network element (200A). Additional detailsregarding the RIB (206) are described below with respect to FIG. 3A.

In one embodiment of the invention, the FIB Compressor (208) may be aprocess executing on the one or more computer processor(s) of thenetwork element (200). The FIB Compressor (208) may includefunctionality to perform functions described below in accordance withone or more embodiments of the invention (see e.g., FIGS. 4A-6F).Specifically, the FIB Compressor (208) may include functionality to: (i)detect updates occurring to the RIB (206) (e.g., additions, deletions,and/or changes to routes in the RIB); (ii) maintain updates to a networkprefix trie (NPT) (including trie nodal information) stored on thenetwork element (200) using network prefixes associated with routes in,and based on the detected updates to, the RIB (206); (iii) obtainbridging next hop information (BNHI) corresponding to route networkprefixes and their respective parent and/or child network prefixes; (iv)perform comparisons between the obtained BNHI; and (v) program the FIB(210), and potentially the FEC Table (212), based on the performedcomparisons.

In one embodiment of the invention, the data plane (204) may be a secondportion of the architecture employed in the network element (200A). Thedata plane (204) may be implemented using hardware, software, firmware,and/or any combination thereof. In one embodiment of the invention, thedata plane (206) may include functionality to receive network packetsvia network interfaces or ports (not shown), process the networkpackets, and, as appropriate, transmit network packets via the same ordifferent network interfaces or ports towards a destination. The networkpackets may be received from a source device or another network element(200B-200N), whereas network packets may be transmitted to a destinationdevice or another network element (200B-200N). The data plane (204)includes a FIB (210), a FEC Table (212), and a network processor (214).Each of these components is described below.

In one embodiment of the invention, the FIB (210) may be a datarepository for storing and mapping routes to FEC indices. As a datarepository, the FIB (210) may take the form of any type of storage unitand/or device such as, for example, a file system, a database, acollection of tables, or any other storage medium. Further, the FIB(210) may include multiple different storage units and/or devices. Inone embodiment of the invention, the FIB (210) may be programmed by oneor more processes (including the FIB Compressor (208)), which may beexecuting on the network element (200A). In one embodiment of theinvention, the FIB (210) may be programmed based on route entries storedin the RIB (206). Additional details regarding the FIB (210) aredescribed below with respect to FIG. 3B.

In one embodiment of the invention, the FEC Table (212) may be a datarepository for storing and mapping FEC indices to next hops.Particularly, the FEC indices are mapped to forwarding (or bridging)information pertaining to next hops along routes to network destinationsreachable from the network element (200A). As a data repository, the FECTable (212) may take the form of any type of storage unit and/or devicesuch as, for example, a file system, a database, a collection of tables,or any other storage medium. Further, the FEC Table (212) may includemultiple different storage units and/or devices. In one embodiment ofthe invention, the FEC Table (212) may be programmed by one or moreprocesses (including the FIB Compressor (208)), which may be executingon the network element (200A). Additional details regarding the FECTable (212) are described below with respect to FIG. 3C.

In one embodiment of the invention, the network processor (214) may behardware (e.g., one or more integrated circuit(s)) that determines outof which network interface or port on the network element (200A) tonetwork packets. The network processor (214) may include interfaces orports that may connect to network interfaces or ports on the networkelement (200A). Each network interface or port (not shown) may beconnected to another network element (200B-200N), a source device, or adestination device (see e.g., FIG. 1 ). The network processor (214) maybe configured to receive network packets via one or more networkinterfaces and determine whether to (i) drop the network packets, (ii)process the network packets in accordance with one or more embodimentsof the invention, and/or (iii) send the network packets, based on theprocessing, out of one or more same or different network interfaces onthe network element (200).

In one embodiment of the invention, how the network processor (214)makes the determination of whether to drop a network packet, and/or senda network packet to another network element (200B-200N) or devicedepends, in part, on whether the network element (200A) is a layer-2(L2) switch or a layer-3 (L3) switch (also referred to as a multilayerswitch), which may perform at least some functions of a router. If thenetwork element (200A) is operating as a L2 switch, the networkprocessor (214) uses the destination media access control (MAC) addressincluded in the network packet, along with the FIB (214) and the FECTable (212) to determine out of which network interface or port to sendthe network packet. If the network element (200A) is operating as a L3switch, the network processor (214) uses the destination InternetProtocol (IP) address included in the network packet, along with the RIB(206), to determine out of which network interface or port to send thenetwork packet. Further, the network processor (214) includes theability to write the MAC address of the next hop (e.g., another networkelement (200B-200N) or device) to send the network packet in place ofits own MAC address (which the last network element (200B-200N) ordevice to send the network packet wrote) in the L2 informationencapsulating the network packet. If the network element (200A) is amultilayer switch, the network processor (214) includes functionality toprocess network packets using both MAC addresses and IP addresses.Examples of a network processor (214) include, but are not limited to, afield programmable gate array (FPGA), an application specific integratedcircuit (ASIC), a digital signal processor (DSP), a microcontroller, adiscrete processor, etc.

FIG. 3A shows a routing information base (RIB) in accordance with one ormore embodiments of the invention. The RIB (300) may include one or moreRIB entries (302A-302N). Each RIB entry (302A-302N) may correspond to aroute to a particular destination. Further, each RIB entry (302A-302N)includes a network prefix (304) and corresponding routing next hopinformation (RNHI) (306).

In one embodiment of the invention, the network prefix (304) may pertainto a reachable destination that the route, associated with the RIB entry(302A-302N), is used for in order to transmit network packets throughand towards the destination. In one embodiment of the invention, thenetwork prefix (304) may be a unique address or identifier assigned to(or associated with) a set of computing systems (e.g., a privatenetwork, a subnet, a datacenter, etc.) that may be operatively connected(e.g., directly or indirectly connected) to the network element on whichthe RIB (300) resides. Subsequently, the network prefix (304) mayidentify a set of computing systems within a local area network (WAN), awide area network (WAN) (such as the Internet), or any other type ofnetwork.

In one embodiment of the invention, RNHI (306) may include routinginformation pertaining to a next hop (e.g., another network element ordevice connected to the network element on which the RIB (300) resides)along a path to a destination. The routing information encompassed inthe RNHI (306) may include, but is not limited to, an Internet Protocol(IP) address associated with the next hop, a cost or metric for usingthe path or route associated with the RIB entry (302A-302N), quality ofservice (QoS) indicators characterizing a current performance of thepath or route, etc.

FIG. 3B shows a forwarding information base (FIB) in accordance with oneor more embodiments of the invention. The FIB (320) may include one ormore FIB entries (322A-322N), each of which may correspond to a route orRIB entry (302A-302N) in the RIB (300). Further, each FIB entry(322A-322N) includes a network prefix (304) and a corresponding FECindex (324).

In one embodiment of the invention, as described above, the networkprefix (304) may pertain to a reachable destination that the route, ofwhich the FIB entry (322A-322N) is associated, is used for in order totransmit network packets through and towards the destination. In oneembodiment of the invention, the network prefix (304) may be a uniqueaddress or identifier assigned to (or associated with) a set ofcomputing systems (e.g., a private network, a subnet, a datacenter,etc.) that may be operatively connected (e.g., directly or indirectlyconnected) to the network element on which the FIB (320) resides.Subsequently, the network prefix (304) may identify a set of computingsystems within a local area network (WAN), a wide area network (WAN)(such as the Internet), or any other type of network.

In one embodiment of the invention, the FEC index (324) may be anidentifier referencing a FEC Table entry (342A-342N) in the FEC Table(340) (see e.g., FIG. 3C). As such, the identifier may be a string ofcharacters (e.g., letters, numbers, symbols, etc.) of any predefinedlength that is used to uniquely identify the FEC Table entry(342A-342N). Alternatively, the FEC index (324) may be an address inmemory associated with or wherein the FEC Table entry (342A-342N) isstored.

FIG. 3C shows a forwarding equivalence class (FEC) table in accordancewith one or more embodiments of the invention. The FEC Table (340) mayinclude one or more FEC Table entries (342A-342N), each corresponding toa particular next hop. Further, each FEC Table entry (342A-342N)includes a FEC index (324) and corresponding bridging next hopinformation (BNHI) (344).

In one embodiment of the invention, as discussed above, the FEC index(324) may be an identifier referencing a FEC Table entry (342A-342N) inthe FEC Table (340) (see e.g., FIG. 3C). As such, the identifier may bea string of characters (e.g., letters, numbers, symbols, etc.) of anypredefined length that is used to uniquely identify the FEC Table entry(342A-342N). Alternatively, the FEC index (324) may be an address inmemory associated with or wherein the FEC Table entry (342A-342N) isstored.

In one embodiment of the invention, BNHI (344) may include bridging orforwarding information pertaining to a next hop (e.g., another networkelement or device) along a path to a destination. The BNHI (344) maycorrespond to the RNHI (306) specified in a RIB entry (302A-302N) in theRIB (300) (see e.g., FIG. 3A). The BNHI (344) may be bridginginformation obtained from performing a next hop resolution on acorresponding RNHI (306). Next hop resolutions are often performed whenprogramming the FIB (320) (see e.g., FIG. 3B) based on routes populatedin the RIB (300). In one embodiment of the invention, the bridging orforwarding information encompassed in the BNHI (344) may include, but isnot limited to, a media access control (MAC) address associated with thenext hop and an identifier associated with a network interface or porton the network element (on which the FEC Table (340) resides) thatconnects to the next hop. The identifier associated with the networkinterface or port may be a string of characters (e.g., letters, numbers,symbols, etc.) of any predefined length that is used to uniquelyidentify the network interface or port.

FIG. 3D shows an example network prefix trie (NPT) in accordance withone or more embodiments of the invention. In one embodiment of theinvention, a NPT (360) may be any data structure ordered in the form ofa hierarchical tree. As a hierarchical tree, the NPT (360) may be acollection of nodes (starting at a root node (362)), wherein each isrepresentative of a network prefix (serving as a key within a key-valuepair), wherein each node stores resolved BNHI for the network prefix(serving as the corresponding value of the key-value pair). In oneembodiment of the invention, each node may further store a set ofreferences to other nodes (discussed below).

In one embodiment of the invention, the nodes (i.e., network prefixes(364, 366, 368, 370, 372, 374, 376, 378, 380, 382)) of the NPT (360) maybe arranged based at least on their network prefix size or length. Withrespect to network prefixes, the network prefix size or length may referto the number of bits (indicative of Internet Protocol (IP) addresses)contained and/or available in the network block associated with thenetwork prefix. A network block may be a set of IP addresses assigned toa network, such as an Internet Service Provider (ISP), a privatenetwork, etc. Moreover, the number of bits remaining for hosting may bededuced from the network prefix size or length. Thus, the lower thenetwork prefix size or length, the more addresses (for hosting) thereare available in the associated network block, and further, the lessspecific the network prefix.

By way of an example, consider an ISP is assigned a network blockassociated with the network prefix “10.0.0.0/8” (expressed in theclassless inter-domain routing (CIDR) notation). Looking at these seriesof numbers, the network prefix size or length is the number “8”, whichis specified after the oblique (i.e., the “/”) in the network prefix.The series of numbers specified before the oblique (i.e., “10.0.0.0”)may be representative of the starting IP address (or root address) forthe assigned network block. Further, per this example, the “8” denotesthat the associated network block includes 32 minus 8, or 24 bits ofhosting address space available using the IP version 4 (IPv4) addressspecification, or alternatively, 128 minus 8, or 120 bits of hostingaddress space available using the IP version 6 (IPv6) addressspecification. Put another way, the “8” denotes that there are 2²⁴ or2¹²⁰ IP addresses available for hosting given the IPv4 or IPv6 addressspecification, respectively. By way of another example, if another ISPwere assigned another network block associated with the network prefix“11.0.0.0/24”, the number of bits available for hosting purposes wouldbe reduced to 32 minus 24, or 8 bits, and 128−24, or 104 bits using theIPv4 and IPv6 address specifications, respectively. That is, the secondISP would be granted 2⁸ or 2¹⁰⁴ IP addresses for hosting, respectively.Thus, again, the lower the network prefix size or length, or the lowerthe number after the oblique, specified in a network prefix, the more IPaddresses available for hosting, and hence, the less specific thenetwork prefix. Conversely, the higher the network prefix size orlength, or the higher the number after the oblique, specified in thenetwork prefix, the less IP addresses available for hosting, and hence,the more specific the network prefix.

In one embodiment of the invention, the network prefixes (364, 366, 368,30, 372, 374, 376, 378, 380, 382) in the NPT (360) may be arranged inascending specificity the deeper the network prefix is positioned in theNPT (360) (e.g., the furthest the network prefix is positioned from theroot node (362)). In reviewing the NPT (360) disclosed in FIG. 3D, forexample, the root node (362) may pertain to the default route, ornetwork prefix, of “0.0.0.0/0” assigned within the IP version 4 (IPv4)protocol. The default route may be the Internet in its entirety. Fromhere, the first layer or tier of network prefixes (e.g., Prefix P₁ (364)and Prefix P₂ (366)), denoted as the immediate children of the root node(362), may pertain to network prefixes following the “X.X.X.X/8”template. The second layer or tier of network prefixes (e.g., Prefix P₁₁(368), Prefix P₁₂ (370), and Prefix P₂₁ (372)) would follow as childrenof the first layer or tier of network prefixes, and may pertain tonetwork prefixes following the “X.X.X.X/12” template. Subsequently, thethird layer or tier of network prefixes (e.g., Prefix P₁₁₁ (374), PrefixP₁₁₂ (376), Prefix P₁₁₃ (378), Prefix P₂₁₁ (380), and Prefix P₂₁₂ (382))would succeed the second layer or tier of network prefixes, and maypertain to network prefixes following the “X.X.X.X/16” template. Notethat at each successive tier, the network prefixes in that tierspecifies a network prefix size or length that is higher than theprevious tier. Subsequently, the network prefixes (364, 366, 368, 30,372, 374, 376, 378, 380, 382) in the NPT (360) may become progressivelymore specific (i.e., specifying higher and higher network prefix sizesand lengths) the deeper (or the furthest from the root node (360)) thenetwork prefix is positioned. In one embodiment of the invention, themore specific a network prefix, the lower the number of hosts (e.g.,computers, servers, etc.) the network prefix can support (e.g., thelower the number of IP addresses available for hosting).

Further, in one embodiment of the invention, a NPT (360) may besegmented into one or more subtrees or branches (384). Each subtree orbranch (384) of the NPT (360) may be representative of a network block,and hence, a set of network prefixes, wherein network prefixespositioned in a lower tier may be subsumed by network prefixespositioned in a higher tier. In one embodiment of the invention, alower-tier network prefix that can be subsumed by a higher-tier networkprefix may be considered a child of the higher-tier network prefix.Alternatively, the higher-tier network prefix, which may subsume thelower-tier network prefix, may be considered the parent of thelower-tier network prefix. For example, referring to the example NPT(360) presented in FIG. 3D, Prefix P₁₁ (368) may pertain to networkprefix “10.0.1.0/24”, which may include Prefix P₁₁₁ (374) pertaining tonetwork prefix “10.0.1.1/32”. That is, Prefix P₁₁₁ (374) may include afirst set of available IP addresses that are a subset of a second set ofIP addresses available through Prefix P₁₁ (368). In this example, PrefixP₁₁ (368) would be considered the parent of Prefix P₁₁₁ (347), whereas,conversely, Prefix P₁₁₁ (374) would be considered the child of PrefixP₁₁ (368). In one embodiment of the invention, the root node (e.g.,Prefix P₁ (364) or Prefix P₂ (366)) of a subtree or branch (384) may bean immediate child of the root node (362) of the NPT (360).

FIG. 3E shows trie nodal information in accordance with one or moreembodiments of the invention. Specifically, as mentioned above, eachnode (including the root node) (390) may be representative of a networkprefix (serving as a key to a key-value pair). In one embodiment of theinvention, stored in (or associated with) each node (390) may bebridging next hop information (BNHI) (392) (see e.g., FIG. 3C) (servingas a corresponding value to the key-value pair). In one embodiment ofthe invention, each node (390) may further store (or be associated with)a set of references, which include a parent reference (394) and zero ormore child references (396A-396N).

In one embodiment of the invention, a parent reference (394) may be aunique identifier/pointer referencing an address in memory associatedwith a parent node (or parent network prefix) of the current/instantnode or network prefix (390). As such, in one embodiment of theinvention, a parent reference (394) may be a string of characters (e.g.,letters, numbers, symbols, or any combination thereof) of any predefinedlength that is used to uniquely identify the parent node (or networkprefix) of the current/instant node or network prefix (390) in the NPT.In one embodiment of the invention, the root node of the NPT may store(or be associated with) a parent reference (394) referencing a NULLmemory space, indicating that the root node of the NPT has no parent.

Similarly, in one embodiment of the invention, a child reference(396A-396N) may be a unique identifier/pointer referencing an address inmemory associated with a child node (or child network prefix) of thecurrent/instant node or network prefix (390). As such, in one embodimentof the invention, a child reference (396A-396N) may be a string ofcharacters (e.g., letters, numbers, symbols, or any combination thereof)of any predefined length that is used to uniquely identify a child node(or network prefix) of the current/instant node or network prefix (390)in the NPT. In one embodiment of the invention, the current/instant nodeor network prefix (390) may have zero, one, or more children. In oneembodiment of the invention, the current/instant node or network prefix(390) may store (or be associated with) a child reference (396A-396N)referencing a NULL memory space, indicating that the current/instantnode or network prefix (390) has zero children.

FIGS. 4A-6F show flowcharts in accordance with one or more embodimentsof the invention. While the various steps in the flowcharts arepresented and described sequentially, one of ordinary skill willappreciate that some or all of the steps may be executed in differentorders, may be combined or omitted, and some or all steps may beexecuted in parallel. In one embodiment of the invention, the stepsshown in FIGS. 4A-6F may be performed in parallel with any other stepsshown in FIGS. 4A-6F without departing from the scope of the invention.

FIGS. 4A-4D show flowcharts describing a method for adding a networkprefix to a network prefix trie in accordance with one or moreembodiments of the invention. Turning to FIG. 4A, in Step 400, a routeadded to the routing information base (RIB) on the network element isdetected. In one embodiment of the invention, the detection may take theform of a pushing mechanism (e.g., generation and transmission of anotification by the RIB to the FIB Compressor in response to the addingof a new route in the RIB). In another embodiment of the invention, thedetection may take the form of a pulling mechanism (e.g., polling of theRIB by the FIB Compressor to identify a specific event—the adding of anew route in the RIB).

In Step 402, a next hop resolution is performed for the added routedetected in Step 400. In one embodiment of the invention, the performingof a next hop resolution results in the obtaining of route bridging nexthop information (RBNHI) (see e.g., FIG. 3C). More specifically, theobtaining of the RBNHI may result from resolving the route next hopinformation (RNHI) (see e.g., FIG. 3A) included in the RIB entrycorresponding to the detected route in the RIB. In one embodiment of theinvention, RBNHI may include bridging or forwarding informationpertaining to a next hop (e.g., another network element or device) alonga path to a destination. The bridging or forwarding informationencompassed in the RBNHI may include, but is not limited to, a mediaaccess control (MAC) address associated with the next hop and anidentifier associated with a network interface or port on the networkelement (on which the FEC Table resides) that connects to the next hop.The identifier associated with the network interface or port may be astring of characters (e.g., letters, numbers, symbols, or anycombination thereof) of any predefined length that is used to uniquelyidentify the network interface or port.

In Step 404, the route network prefix for the route detected in Step 400(obtained from the RIB entry associated with the route (see e.g., FIG.3A)) is added to the network prefix trie (NPT) stored on the networkelement. In one embodiment of the invention, the route network prefixmay be added to the NPT based on the network prefix size or lengthspecified in the network prefix (discussed above). In one embodiment ofthe invention, the route network prefix may be placed in a tier above(and therefore subsumes) any existing network prefixes that include atleast a portion of the IP addresses available in the route networkprefix. Additionally, or alternatively, the route network prefix may beplaced in a tier below (and therefore is subsumed by) an existingnetwork prefix in the NPT, wherein the route network prefix includes atleast a portion of the IP addresses available in the existing networkprefix.

In one embodiment of the invention, the addition of the route networkprefix to the NPT may further entail initialization of the trie nodalinformation (see e.g., FIG. 3E) stored (or associated) with the routenetwork prefix. As discussed above, trie nodal information may includethree elements: (i) BNHI; (ii) a parent reference; and (iii) a set ofchild references. Subsequently, in one embodiment of the invention, theBNHI of the trie nodal information for the route network prefix may beinitialized as the RBNHI obtained in Step 402. Further, the parentreference of the trie nodal information for the route network prefix maybe initialized as the identifier/pointer associated with the existingnetwork prefix in the NPT that subsumes the route network prefix.Moreover, the set of child references of the trie nodal information forthe route network prefix may be initialized as theidentifier(s)/pointer(s) associated with the, if any, existing networkprefix(es) in the NPT that is subsumed by the route network prefix.

In one embodiment of the invention, the adding of the route networkprefix to the NPT may further entail updating the trie nodal informationstored (or associated) with the parent network prefix (e.g., theexisting network prefix in the NPT that subsumes the route networkprefix) and each of the set of child network prefixes (e.g., theexisting network prefix(es) in the NPT that is subsumed by the routenetwork prefix), if any. More specifically, in one embodiment of theinvention, with respect to updating the parent trie nodal information,the set of child references of the parent trie nodal information may beupdated to include the identifier/pointer associated with the routenetwork prefix (in place of the identifier(s)/pointer(s) associated withthe set of child network prefix(es), which used to be the child(ren) ofthe parent network prefix). With respect to updating each child trienodal information (of the set of child network prefix(es)), the parentreference of each child trie nodal information may be updated to includethe identifier/pointer associated with the route network prefix (inplace of identifier/pointer associated with the parent network prefix,which used to be the parent of each of the child network prefixes).

In Step 406, the parent network prefix for/of the route network prefixis identified. In one embodiment of the invention, identification of theparent network prefix may entail accessing the trie nodal informationassociated with the route network prefix and obtaining the parentreference specified in the route trie nodal information.

In Step 408, the parent bridging next hop information (PBNHI) associatedwith the parent network prefix is obtained. In one embodiment of theinvention, obtaining of the PBNHI may entail accessing the trie nodalinformation associated with the parent network prefix identified in Step406 (using the parent reference specified in the route trie nodalinformation) and obtaining the corresponding BNHI (e.g., value)specified in the parent trie nodal information.

In Step 410, a determination is made as to whether the RBNHI (obtainedin Step 402) matches the PBNHI (obtained in Step 408). If it isdetermined that the RBNHI does match the PBNHI, the process proceeds toStep 412. In one embodiment of the invention, the RBNHI matching thePBNHI may be indicative that both the parent network prefix and theroute network prefix are reachable through a common next hop.Subsequently, the forwarding information base (FIB) on the networkelement need not be updated in response to the addition of the routenetwork prefix (e.g., the added route) to the NPT.

In one embodiment of the invention, the FIB may be limited or compressedto include FIB entries corresponding to routes associated with a set ofthe least specific network prefixes in the RIB. Subsequently, thereexists an assumption that each least specific network prefix in the NPTis already associated with a designated FIB entry in the FIB. In view ofthis, (i) because the RBNHI matches the PBNHI, and (ii) because theparent network prefix is the least specific network prefix between theparent network prefix and the route network prefix—the existing FIBentry in the FIB associated with the parent network prefix in effectdoes reference the necessary BNHI (e.g., PBNHI, which matches the RBNHI)to direct any network packets (via the common next hop) towardsdestinations subsumed by the parent network prefix as well as the routenetwork prefix. Therefore, the route network prefix does not require itsown FIB entry in the FIB.

On the other hand, further to Step 410, if it is determined that theRBNHI does not match the PBNHI, the process proceeds to Step 420 (seee.g., FIG. 4B). In one embodiment of the invention, the RBNHI notmatching the PBNHI may be indicative that the parent network prefix andthe route network prefix are reachable through different next hops. Inlight of the different next hops, the existing FIB entry in the FIBassociated with the parent network prefix (because it is the leastspecific network prefix between the parent network prefix and the routenetwork prefix) in effect does not reference the necessary BNHI (e.g.,RBNHI, which does not match the PBNHI) to direct network packets towardsdestinations subsumed by the route network prefix. Subsequently, the FIB(and potentially, the forwarding equivalence class (FEC) Table) must beupdated to include a designated FIB entry for the route network prefix.

In Step 412, the conventional creation of a new FIB entry in the FIB forthe added route (associated with the route network prefix) is waived. Inone embodiment of the invention, the waiver is performed as a result ofdetermining (in Step 410) that the RBNHI does match the PBNHI. As notedabove, the RBNHI matching the PBNHI does not require its own FIB entryin the FIB. One of ordinary skill in the relevant art would appreciatethat, during conventional operation of a network element (e.g., prior toembodiments of the invention), the FIB is programmed/populated bycreating FIB entries with a one-to-one correspondence to RIB entriesexisting in the RIB. Therefore, conventionally, when a route (associatedwith a new RIB entry) is added to the RIB, a new FIB entry in the FIB iscreated to correspond with the new RIB entry for the added route in theRIB. Further, because this conventional FIB entry creation mechanism iswaived in accordance with embodiments of the invention, one of ordinaryskill in the relevant art would thus appreciate that fewer FIB entriesare being generated to correspond with each RIB entry in the RIB, whichresults in a compression of the FIB (relative to the RIB).

Turning to FIG. 4B, in Step 420, a search for an existing FEC Tableentry that includes the RBNHI is performed. In one embodiment of theinvention, the search is performed as a result of determining (in Step410) that the RBNHI does not match the PBNHI. As noted above, the RBNHInot matching the PBNHI requires updating of the FIB (and, potentially,the FEC Table) to include a designated FIB entry for the route networkprefix. To that end, performing of the search may entail comparing theRBNHI with each BNHI specified in each existing FEC Table entry in theFEC Table. Subsequently, if an existing FEC Table entry specifies BNHIthat matches the RBNHI, then that FEC Table entry may be identified asthe existing FEC Table entry in the FEC Table that includes the RBNHI.

In Step 422, a determination is made as to whether an existing FEC Tableentry that includes the RBNHI (and sought for in Step 420) has beenidentified. If it is determined that an existing FEC Table entry hasbeen identified, the process proceeds to Step 424. On the other hand, ifit is determined that an existing FEC Table entry has not beenidentified, the process proceeds to Step 428.

In Step 424, after determining (in Step 422) that an existing FEC Tableentry (including the RBNHI) has been identified, the FEC index specifiedin the identified FEC Table entry is obtained. Alternatively, in Step428, after determining (in Step 422) that no existing FEC Table entry(including the RBNHI) has been identified, a new FEC Table entry iscreated in the FEC Table. In one embodiment of the invention, the newFEC Table entry is created to include a new FEC indexreferencing/identifying the new FEC Table entry, and the RBNHI.

In Step 426, a new FIB entry in the FIB is created for the route networkprefix. In one embodiment of the invention, the new FIB entry is createdsubsequent to obtaining the FEC index specified in the existing FECTable entry sought for and identified in Step 420. In another embodimentof the invention, the new FIB entry is created subsequent to creating anew FEC Table entry in Step 428, which includes a new FEC index and theRBNHI. In one embodiment of the invention, the new FIB entry is createdto include the route network prefix and the FEC index (obtained in Step424 or generated in Step 428).

In Step 430, after updating the FIB and/or the FEC Table to account forthe route network prefix, any children, if any, of the route networkprefix are identified. In one embodiment of the invention,identification of the children may entail accessing the trie nodalinformation associated with the route network prefix and obtaining theset of child references, if any, specified in the route trie nodalinformation.

Turning to FIG. 4C, in Step 440, a determination is made as to whetherany children under the route network prefix have been identified(pursuant to Step 430). If it is determined that zero children wereidentified (i.e., the set of child references specified in the routetrie nodal information references NULL memory space), then the processends as no further updates to at least the FIB are necessary. On theother hand, if it is determined that at least one child under the routenetwork prefix has been identified, then the process proceeds to Step442.

While the following steps (starting at Step 442) reference a particularchild network prefix, one of ordinary skill in the art would appreciatethat the following steps may be repeated for each child network prefixunder the route network prefix that may have been identified in Step430. Further, with respect to the following steps, consider that priorto the addition of the route network prefix to the NPT (see e.g., Step404), there exists two possibilities respective to each child networkprefix: (i) the child network prefix corresponds to BNHI that did matchthe PBNHI, and subsequently, did not require a FIB entry of its ownbecause the existing FIB entry for the parent network prefix (which wasthe parent network prefix for the child network prefix prior to theaddition of the route network prefix to the NPT) did reference BNHIappropriate to direct network packets towards destinations subsumed byboth the parent network prefix and the child network prefix; or (ii) thechild network prefix corresponds to BNHI that did not match the PBNHI,and subsequently, did require a FIB entry of its own because theexisting FIB entry for the parent network prefix references BNHIappropriate to direct network packets towards destinations subsumed bythe parent network prefix, however, fails to reference BNHI appropriateto direct network packets towards destinations subsumed by the childnetwork prefix. Therefore, in proceeding on to the following steps,consider that a child network prefix may not (further to the firstpossibility) or may (further to the second possibility) have an existingFIB entry in the FIB for which the child network prefix is associated.

In Step 442, in view of the above, child bridging next hop information(CBNHI) for a/the child network prefix is obtained. In one embodiment ofthe invention, obtaining of the CBNHI may entail accessing the trienodal information associated with a/the child network prefix (usinga/the child reference specified in the route trie nodal information) andobtaining the corresponding BNHI (e.g., value) specified in a/the childtrie nodal information.

In Step 444, a determination is made as to whether the CBNHI (obtainedin Step 442) matches the PBNHI (obtained in Step 408). If it isdetermined that the CBNHI does match the PBNHI, the process proceeds toStep 446. In one embodiment of the invention, the CBNHI matching thePBNHI may be indicative that both the parent network prefix and thechild network prefix are reachable through the same next hop. Further,in view of the two possibilities respective to each child network prefixdiscussed above, because the CBNHI matches the PBNHI, it was notpreviously necessary to create a FIB entry in the FIB for the childnetwork prefix.

The route network prefix, however, has since become the new “parent” ofthe child network prefix subsequent to the addition of the route networkprefix to the NPT. Consequently, the child network prefix must now relyon the existing FIB entry for the route network prefix (rather than theparent network prefix) to correspond to the appropriate BNHI (e.g.,CBNHI) in order to direct network packets towards destinations subsumedby the child network prefix. In one embodiment of the invention, for theexisting FIB entry for the route network prefix (created in Step 426) tocover the destinations subsumed by the child network prefix, the RBNHImust match the CBNHI. However, in this case, it is deduced that theRBNHI does not match the CBNHI because the CBNHI matches the PBNHI, andthe RBNHI has been determined to not match the PBNHI (see e.g., Step410). As a result, the existing FIB entry for the route network prefixdoes not reference the appropriate BNHI in order to direct networkpackets towards destinations subsumed by the child network prefix. Inview of this, the FIB (and potentially, the FEC Table) must be updatedto include a designated FIB entry for the child network prefix.

On the other hand, further to Step 444, if it is determined that theCBNHI does not match the PBNHI, the process proceeds to Step 460 (seee.g., FIG. 4D). In one embodiment of the invention, the CBNHI notmatching the PBNHI may be indicative that different next hops are usedto direct network packets towards destinations subsumed by the childnetwork prefix versus the parent network prefix. Further, in view of thetwo possibilities respective to each child network prefix discussedabove, because the CBNHI does not match the PBNHI, it was previouslynecessary to create a FIB entry in the FIB for the child network prefix.Therefore, presently, there is an existing FIB entry for which the childnetwork prefix is associated. Additional details respective to thepursuit of this path from Step 444 is discussed below with respect toStep 460 in FIG. 4D.

Proceeding with FIG. 4C, in Step 446, the existing FIB entry in the FIB,for which the parent network prefix is associated, is identified. In oneembodiment of the invention, the aforementioned identification may beperformed as a result of determining (in Step 444) that the CBNHI doesmatch the PBNHI. As noted above, this determination requires updating ofthe FIB, and, potentially, the FEC Table because the existing FIB entryfor the route network prefix does not reference the appropriate BNHI inorder to direct network packets towards destinations subsumed by thechild network prefix. To that end, identification of the existing FIBentry for the parent network prefix may entail comparing the parentnetwork prefix with each network prefix specified in each existing FIBentry in the FIB. Subsequently, the existing FIB entry in the FIB thatspecifies a network prefix matching the parent network prefix may beselected as the existing FIB entry in the FIB associated with the parentnetwork prefix.

In Step 448, the FEC index specified in the existing FIB entry(identified in Step 446) is obtained. In one embodiment of theinvention, the FEC index specified in the existing FIB entry for theparent network prefix is obtained because the FEC index references anexisting FEC Table entry that includes BNHI (e.g., PBNHI, which matchesthe CBNHI) appropriate to direct network packets towards destinationssubsumed by the child network prefix. Further, in Step 450, a new FIBentry for the child network prefix is created. In one embodiment of theinvention, the new FIB entry is created to include the child networkprefix and the FEC index obtained in Step 448. With the creation of theFIB entry for the child network prefix, the process respective to thecurrent/instant child network prefix ends.

Turning to FIG. 4D, in Step 460, a determination is made as to whetherthe CBNHI (obtained in Step 442) matches the RBNHI (obtained in Step402). In one embodiment of the invention, this determination isperformed as a result of determining (in Step 444) that the CBNHI doesnot match the PBNHI. Thus, if it is determined that the CBNHI does matchthe RBNHI, then the process proceeds to Step 462. In one embodiment ofthe invention, the CBNHI matching the RBNHI may be indicative that boththe route network prefix and the child network prefix are reachablethrough the same next hop.

In one embodiment of the invention, as discussed above, because theCBNHI does not match the PBNHI (per Step 444), there presently exists aFIB entry in the FIB for which the child network prefix is associated.Further, because the FIB, in one embodiment of the invention, may belimited or compressed to include FIB entries corresponding to routesassociated with a set of the least specific network prefixes in the RIB,the existing FIB entry associated with the route network prefix (createdin Step 426) is retained over the existing FIB entry associated with thechild network prefix. In other words, because the CBNHI matches theRBNHI, the existing FIB entry for the route network prefix referencesthe BNHI (e.g., RBNHI, which matches the CBNHI) appropriate to directnetwork packets towards destinations subsumed by both the route networkprefix and the child network prefix. Summarily, the existing FIB entryfor the child network prefix is no longer necessary, and may bedeleted/removed from the FIB.

To that end, in Step 462, after determining (in Step 460) that the CBNHIdoes match the RBNHI, the existing FIB entry in the FIB, for which thechild network prefix is associated, is identified. In one embodiment ofthe invention, identification of the existing FIB entry associated withthe child network prefix may entail comparing the child network prefixwith each network prefix specified in each existing FIB entry in theFIB. Subsequently, the existing FIB entry in the FIB that specifies anetwork prefix matching the child network prefix may be identified asthe existing FIB entry in the FIB associated with the child networkprefix. Following this, in Step 464, the existing FIB entry associatedwith the child network prefix (identified in Step 462) isremoved/deleted from the FIB on the network element, and the processrespective to the current/instant child network prefix ends.

On the other hand, returning to Step 460, if it is determined that theCBNHI does not match the RBNHI, the process respective to thecurrent/instant child network prefix ends. In one embodiment of theinvention, the CBNHI not matching the RBNHI may be indicative that thechild network prefix and the route network prefix are reachable throughdifferent next hops. Further, in light of the different next hops, theexisting FIB entry for the route network prefix does not reference theBNHI (e.g., RBNHI, which does not match the CBNHI) appropriate to directnetwork packets towards destinations subsumed by the child networkprefix. Accordingly, a FIB entry for which the child network prefix isassociated must be created. However, because the CBNHI has beendetermined to not match the PBNHI (see e.g., Step 444), there presentlyexists a FIB entry in the FIB for which the child network prefix isassociated. Therefore, no subsequent updates to the FIB are necessary,and the process respective to the current/instant child network prefixends.

FIGS. 5A-5D show flowcharts describing a method for deleting a networkprefix from a network prefix trie in accordance with one or moreembodiments of the invention. Turning to FIG. 5A, in Step 500, a routeremoved from the routing information base (RIB) on the network elementis detected. In one embodiment of the invention, the detection may takethe form of a pushing mechanism (e.g., generation and transmission of anotification by the RIB to the forwarding information base (FIB)Compressor in response to the removal of an existing route in the RIB).In another embodiment of the invention, the detection may take the formof a pulling mechanism (e.g., polling of the RIB by the FIB Compressorto identify a specific event—the removal of any existing route in theRIB).

In Step 502, the route network prefix for the route detected in Step 500(obtained from the removed RIB entry associated with the route (seee.g., FIG. 3A)) is used to locate the route network prefix in thenetwork prefix trie (NPT). In one embodiment of the invention, locatingor searching for the route network prefix in the NPT may involvetraversing the NPT using any existing, or later discovered, tree/triedata structure searching algorithms.

In Step 504, the route bridging next hop information (RBNHI) for theroute network prefix is obtained. In one embodiment of the invention,obtaining of the RBNHI may entail accessing the trie nodal informationstored (or associated) with the route network prefix located in Step 502and obtaining the corresponding BNHI (e.g., value) specified in theroute trie nodal information.

In Step 506, the parent network prefix for/of the route network prefixis identified. In one embodiment of the invention, identification of theparent network prefix may entail accessing the trie nodal informationassociated with the route network prefix and obtaining the parentreference specified in the route trie nodal information.

In Step 508, the parent bridging next hop information (PBNHI) associatedwith the parent network prefix is obtained. In one embodiment of theinvention, obtaining of the PBNHI may entail accessing the trie nodalinformation associated with the parent network prefix identified in Step506 (using the parent reference specified in the route trie nodalinformation) and obtaining the corresponding BNHI (e.g., value)specified in the parent trie nodal information.

Turning to FIG. 5B, in Step 520, a determination is made as to whetherthe RBNHI (obtained in Step 504) matches the PBNHI (obtained in Step508). If it is determined that the RBNHI does match the PBNHI, theprocess proceeds to Step 546 (see e.g., FIG. 5C). In one embodiment ofthe invention, the RBNHI matching the PBNHI may be indicative that boththe parent network prefix and the route network prefix are reachablethrough a common next hop. Thus, as it stands in this case, an existingFIB entry in the FIB associated with the parent network prefixreferences the necessary BNHI (e.g., PBNHI, which matches the RBNHI) todirect network packets (via the common next hop) towards destinationssubsumed by the parent network prefix as well as the route networkprefix. Further, because the route network prefix does not have anexisting FIB entry in the FIB for which it is associated, removal of theroute network prefix from the NPT (as a result of the removal of acorresponding route in the RIB) may not require affecting the FIB.

On the other hand, further to Step 520, if it is determined that theRBNHI does not match the PBNHI, the process proceeds to Step 522. In oneembodiment of the invention, the RBNHI not matching the PBNHI may beindicative that the route network prefix and the parent network prefixare reachable through different next hops. In light of the differentnext hops, the existing FIB entry in the FIB associated with the parentnetwork prefix in effect does not reference the necessary BNHI (e.g.,RBNHI, which does not match the PBNHI) to direct network packets towardsdestinations subsumed by the route network prefix. Subsequently, in viewof this mismatching, the route network prefix had required its own FIBentry in the FIB for which it is associated. Summarily, because theroute network prefix has an existing FIB entry in the FIB for which itis associated, removal of the route network prefix from the NPT (as aresult of the removal of a corresponding route in the RIB) may requireupdating the FIB to delete the aforementioned existing FIB entry.

Proceeding with FIG. 5B, in Step 522, after determining (in Step 520)that the RBNHI does match the PBNHI, the existing FIB entry in the FIBassociated with the route network prefix is identified. In oneembodiment of the invention, identification of the existing FIB entryassociated with the route network prefix may entail comparing the routenetwork prefix with each network prefix specified in each existing FIBentry in the FIB. Subsequently, the existing FIB entry in the FIB thatspecifies a network prefix matching the route network prefix may beidentified as the existing FIB entry in the FIB associated with theroute network prefix.

In Step 524, the forwarding equivalence class (FEC) index specified inthe existing FIB entry (identified in Step 522) is obtained. In oneembodiment of the invention, the specified FEC index may be obtained,and stored elsewhere temporarily, in order to accommodate future stepsin the process (see e.g., Step 544 in FIG. 5C). Subsequently, in Step526, the existing FIB entry (identified in Step 522) is removed/deletedfrom the FIB on the network element.

In Step 528, after deletion of the existing FIB entry associated withthe route network prefix from the FIB, any children, if any, of theroute network prefix are identified. In one embodiment of the invention,identification of the children may entail accessing the trie nodalinformation associated with the route network prefix and obtaining theset of child references, if any, specified in the route trie nodalinformation.

In Step 530, a determination is made as to whether any children wereidentified in Step 528. If it is determined that zero children wereidentified (e.g., the set of child references specified in the routetrie nodal information references NULL memory space), then the processends. On the other hand, if it is determined that at least one childunder the route network prefix has been identified, then the processproceeds to Step 540 (see e.g., FIG. 5C).

While the following steps (starting at Step 540) reference a particularchild network prefix, one of ordinary skill in the art would appreciatethat the following steps may be repeated for each child network prefixunder the route network prefix that may have been identified in Step528.

Turning to FIG. 5C, in Step 540, child bridging next hop information(CBNHI) for a/the child network prefix is obtained. In one embodiment ofthe invention, obtaining the CBNHI may entail accessing the trie nodalinformation associated with a/the child network prefix (using a/thechild reference specified in the route trie nodal information) andobtaining the corresponding BNHI (e.g., value) specified in a/the childtrie nodal information.

In Step 542, a determination is made as to whether the CBNHI (obtainedin Step 540) matches the RBNHI (obtained in Step 504). If it isdetermined that the CBNHI does match the RBNHI, the process proceeds toStep 544. In one embodiment of the invention, the CBNHI matching theRBNHI may be indicative that both the child network prefix and the routenetwork prefix are reachable through the same next hop. Thus, prior tothe earlier removal of the FIB entry in the FIB associated with theroute network prefix (see e.g., Step 526), the destinations subsumed bythe child network prefix were covered by the aforementioned FIB entryassociated with the route network prefix. However, with the deletion ofthe FIB entry in the FIB associated with the route network prefix, thecapability to direct network packets addressed towards destinationssubsumed by the child network prefix no longer exists. Subsequently, thecreation of a new FIB entry in the FIB associated with the child networkprefix is necessary to resume the aforementioned capability.

On the other hand, further to Step 542, if it is determined that theCBNHI does not match the RBNHI, the process proceeds to Step 560 (seee.g., FIG. 5D). In one embodiment of the invention, the CBNHI notmatching the RBNHI may be indicative that different next hops are usedto direct network packets towards destinations subsumed by the childnetwork prefix versus the route network prefix. Therefore, the childnetwork prefix had required its own FIB entry in the FIB, separate fromthe existing FIB entry (present prior to its subsequent deletion in Step526) associated with the route network prefix. Further, as mentionedabove, with the deletion of the FIB entry in the FIB associated with theroute network prefix, the capability to direct network packets addressedtowards destinations subsumed by the child network prefix would nolonger exist, thereby mandating the creation of a new FIB entry in theFIB associated with the child network prefix. However, in this case,because the child network prefix is already associated with an existingFIB entry in the FIB, which retains the aforementioned capabilitydespite the deletion of the existing FIB entry associated with the routenetwork prefix, the removal of the route network prefix (from the NPT)may not require affecting the FIB.

In Step 544, a new FIB entry for which the child network prefix isassociated is created in the FIB. In one embodiment of the invention,the creation of the new FIB entry may be performed as a result ofdetermining (in Step 542) that the CBNHI matches the RBNHI. As notedabove, this determination requires updating the FIB to resume thecapability to direct network packets addressed towards destinationssubsumed by the child network prefix, which temporarily no longerexists. To that end, in one embodiment of the invention, the new FIBentry is created to include the child network prefix and the FEC index(obtained in Step 524) referencing the existing FEC Table entry thatincludes the BNHI (e.g., RBNHI, which matches the CBNHI) necessary toresume the aforementioned capability.

In Step 546, (i) after creating/populating a new FIB entry for eachchild network prefix (of the route network prefix) (in Step 544); or(ii) after determining (in Step 520) that the RBNHI does match thePBNHI: the route network prefix is deleted/removed from the NPT. Asmentioned above, in one embodiment of the invention, theremoval/deletion of the route network prefix from the NPT may furtherentail updating the trie nodal information stored (or associated) withthe parent network prefix (e.g., the existing network prefix in the NPTthat had subsumed the route network prefix) and each of the set of childnetwork prefixes (e.g., the existing network prefix(es) in the NPT thathad been subsumed by the route network prefix), if any. Morespecifically, in one embodiment of the invention, with respect toupdating the parent trie nodal information, the set of child referencesof the parent trie nodal information may be updated to include theidentifier(s)/pointer(s) associated with the child network prefix(es)(in place of the identifier/pointer associated with the route networkprefix, which used to be the child of the parent network prefix). Withrespect to updating each child trie nodal information (of the set ofchild network prefix(es)), the parent reference of each child trie nodalinformation may be updated to include the identifier/pointer associatedwith the parent network prefix (in place of identifier/pointerassociated with the route network prefix, which used to be the parent ofeach of the child network prefixes). From here, the process subsequentlyends.

Turning to FIG. 5D, in Step 560, after determining (in Step 542) thatthe CBNHI does not match the RBNHI (e.g., a FIB entry for the childnetwork prefix was warranted), a fourth determination is made as towhether the CBNHI (obtained in Step 540), instead, matches the PBNHI(obtained in Step 508). If it is determined that the CBNHI matches thePBNHI, the process proceeds to Step 562. In one embodiment of theinvention, the CBNHI matching the PBNHI may be indicative that both thechild network prefix and the parent network prefix are reachable throughthe same next hop (adjacent to the network element) along one or morepath(s) that includes at least the next hop. Further, since the FIB, inone embodiment of the invention, is limited or compressed to include FIBentries corresponding to routes associated with a set of the leastspecific network prefixes in the RIB, the FIB entry associated with theparent network prefix (which is the least specific network prefixbetween the child network prefix and the parent network prefix) isretained over the existing FIB entry associated with the child networkprefix.

On the other hand, further to Step 560, if it is determined that theCBNHI does not match the PBNHI, the process ends. In one embodiment ofthe invention, the CBNHI not matching the PBNHI may be indicative thatthe child network prefix is reachable through a first next hop (adjacentto the network element) that is different than a second next hop (alsoadjacent to the network element) through which the parent network prefixis reachable. That is, in one embodiment of the invention, the twodifferent BNHI (e.g., the CBNHI and the PBNHI) implies two different FECTable entries currently exist in the FEC Table, each including eitherthe CBNHI or the PBNHI. Further, the first existing FEC Table entryincluding the CBNHI is referenced by a first existing FIB entryassociated with the child network prefix, whereas the second existingFEC Table entry including the PBNHI is referenced by a second existingFIB entry associated with the parent network prefix. Furthermore,because the child network prefix is already associated with an existingFIB entry in the FIB, no further steps are required to ensure thatnetwork packets addressed towards the child network prefix can bedirected to the child network prefix when necessary.

In Step 562, after determining (in Step 560) that the CBNHI does matchthe PBNHI, the existing FIB entry in the FIB associated with the childnetwork prefix is identified. In one embodiment of the invention,identification of the existing FIB entry associated with the childnetwork prefix may entail comparing the child network prefix with eachnetwork prefix specified in each existing FIB entry in the FIB.Subsequently, the existing FIB entry in the FIB that specifies a networkprefix matching the child network prefix may be selected as the existingFIB entry in the FIB associated with the child network prefix. Followingthis, in Step 564, the existing FIB entry associated with the childnetwork prefix (identified in Step 562) is removed/deleted from the FIBon the network element. Subsequently, the process ends.

FIGS. 6A-6F show flowcharts describing a method for updating a networkprefix in a network prefix trie in accordance with one or moreembodiments of the invention. Turning to FIG. 6A, in Step 600, a routesubjected to an update in the routing information base (RIB) on thenetwork element is detected. In one embodiment of the invention, thedetection may take the form of a pushing mechanism (e.g., generation andtransmission of a notification by the RIB to the forwarding informationbase (FIB) Compressor in response to the update of an existing route inthe RIB). In another embodiment of the invention, the detection may takethe form of a pulling mechanism (e.g., polling of the RIB by the FIBCompressor to identify a specific event—any update to any existing routein the RIB).

In Step 602, a next hop resolution is performed for the updated routedetected in Step 600. In one embodiment of the invention, the performingof a next hop resolution results in the obtaining of new bridging nexthop information (NBNHI) (see e.g., FIG. 3C) for the existing route inthe RIB. More specifically, the obtaining of the NBNHI may result fromresolving the new/updated route next hop information (RNHI) (see e.g.,FIG. 3A) included in the RIB entry corresponding to the detected routein the RIB. In one embodiment of the invention, NBNHI may includebridging or forwarding information pertaining to a next hop (e.g.,another network element or device) along a new path to a destinationsubsumed by the updated route. The bridging or forwarding informationencompassed in the NBNHI may include, but is not limited to, a mediaaccess control (MAC) address associated with the next hop and anidentifier associated with a network interface or port on the networkelement (on which the forwarding equivalence class (FEC) Table resides)that connects to the next hop. The identifier associated with thenetwork interface or port may be a string of characters (e.g., letters,numbers, symbols, etc.) of any predefined length that is used touniquely identify the network interface or port.

In Step 604, the route network prefix for the route detected in Step 600(obtained from the updated RIB entry associated with the route (seee.g., FIG. 3A)) is used to locate the route network prefix in thenetwork prefix trie (NPT). In one embodiment of the invention, locatingor searching for the route network prefix in the NPT may involvetraversing the NPT using one or more of any existing tree/trie datastructure searching algorithm(s).

In Step 606, after locating the route network prefix in the NPT, theexisting bridging next hop information (EBNHI) for the route networkprefix is obtained. In one embodiment of the invention, obtaining of theEBNHI may entail accessing the trie nodal information stored (orassociated) with the route network prefix located in Step 604 andobtaining the corresponding BNHI (e.g., value) specified in the routetrie nodal information.

In Step 608, the parent of the route network prefix is identified. Inone embodiment of the invention, identification of the parent mayinvolve accessing the trie nodal information associated with the routenetwork prefix and obtaining the parent reference specified in the routetrie nodal information.

In Step 610, the parent bridging next hop information (PBNHI) associatedwith the parent node (or network prefix) is obtained. In one embodimentof the invention, obtaining of the PBNHI may involve accessing the trienodal information associated with the parent node (or network prefix)identified in Step 608 (using the parent reference specified in theroute trie nodal information) and obtaining the corresponding BNHI(e.g., value) specified in the parent trie nodal information.

Turning to FIG. 6B, in Step 620, a first determination is made as towhether the PBNHI (obtained in Step 610) matches the EBNHI (obtained inStep 606). If it is determined that the PBNHI does match the EBNHI, theprocess proceeds to Step 622. In one embodiment of the invention, thePBNHI matching the EBNHI may be indicative that both the parent networkprefix and the route network prefix (prior to the update detected inStep 600) were reachable through the same next hop (adjacent to thenetwork element) along one or more path(s) that includes at least thenext hop. Further, as prior to the update, the parent network prefix wasthe least specific network prefix between the parent network prefix andthe route network prefix, no FIB entry associated with the route networkprefix was warranted. However, because the PBNHI matches the EBNHI, thePBNHI conversely (and currently) does not match the NBNHI (e.g., theupdated BNHI for the route network prefix). Subsequently, in view ofthis, creation of a FIB entry associated with the route network prefix(corresponding to the NBNHI) is needed to ensure that network packetsaddressed towards the route network prefix can be directed to the routenetwork prefix when necessary.

On the other hand, further to Step 620, if it is determined that thePBNHI does not match the EBNHI, the process proceeds to Step 640 (seee.g., FIG. 6C). In one embodiment of the invention, the PBNHI notmatching the EBNHI may be indicative that, prior to the update to theroute detected in Step 600, the parent network prefix is reachablethrough a first next hop (adjacent to the network element) that isdifferent than a second next hop (also adjacent to the network element)through which the route network prefix was reachable. That is, in oneembodiment of the invention, the two different BNHI (e.g., the PBNHI andthe EBNHI) implies two different FEC Table entries currently exist inthe FEC Table, each including either the PBNHI or the EBNHI. Further,the first existing FEC Table entry including the PBNHI is referenced bya first existing FIB entry associated with the parent network prefix,whereas the second existing FEC Table entry including the EBNHI isreferenced by a second existing FIB entry associated with the routenetwork prefix.

Proceeding with FIG. 6B, in Step 622, after determining (in Step 620)that the PBNHI does match the EBNHI, a search for an existing FEC Tableentry in the FEC Table that includes the NBNHI is attempted. In oneembodiment of the invention, searching for an existing FEC Table entrythat includes the NBNHI may entail comparing the NBNHI to each existingBNHI specified in each existing FEC Table entry in the FEC Table.Subsequently, if an existing FEC Table entry in the FEC Table specifiesBNHI that matches the NBNHI, then that FEC Table entry may be identifiedas the existing FEC Table entry in the FEC Table that includes theNBNHI, and may be further associated with the route network prefix.

In Step 624, a second determination is made as to whether an existingFEC Table entry (that includes the NBNHI) was identified in Step 622. Ifit is determined that an existing FEC Table entry was indeed identified,then the process proceeds to Step 626. On the other hand, if it isdetermined that no existing FEC Table entry was identified, the processproceeds to Step 630.

In Step 626, after determining (in Step 624) that an existing FEC Tableentry has been identified that includes the NBNHI, the FEC indexspecified in the existing FEC Table entry (identified in Step 622) isobtained. Alternatively, in Step 630, after determining (in Step 624)that an existing FEC Table entry had not been identified that includesthe NBNHI, a new FEC Table entry (for the route network prefix) iscreated. In one embodiment of the invention, the new FEC Table entry mayinclude a new FEC index and the NBNHI (obtained in Step 602). Asdiscussed above, the new FEC index may be an identifier referencing thenew FEC Table entry (for the route network prefix) in the FEC Table. Assuch, the identifier may be a string of characters (e.g., letters,numbers, symbols, or any combination thereof) of any predefined lengththat is used to uniquely identify the new FEC Table entry (for the routenetwork prefix). Alternatively, the FEC index may be an address inmemory associated with or wherein the new FEC Table entry (for the routenetwork prefix) is stored.

In Step 628, following the obtaining of a FEC index specified in anexisting FEC Table entry (see e.g., Step 626) or the creation of a newFEC Table entry including a new FEC index (see e.g., Step 630), a newFIB entry for the route network prefix is created in the FIB on thenetwork element. In one embodiment of the invention, the new FIB entry(for the route network prefix) may include the route network prefix and(i) the obtained FEC index (of Step 626) that references theaforementioned existing FEC Table entry; or (ii) the new FEC index thatreferences the created/populated FEC Table entry (for the route networkprefix) in Step 630. From here, the process proceeds to Step 646 (seee.g., FIG. 6C).

Turning to FIG. 6C, in Step 640, after determining (in Step 620) thatthe PBNHI does not match the EBNHI, a third determination is made as towhether the PBNHI, instead, matches the NBNHI. If it is determined thatthe PBNHI matches the NBNHI, the process proceeds to Step 642. In oneembodiment of the invention, the PBNHI matching the NBNHI, while notmatching the EBNHI (see e.g., Step 620), may be indicative that, asmentioned above, prior to the update of the route corresponding to theroute network prefix, the difference in BNHI amongst the parent networkprefix and the route network prefix would have warranted creation of aFIB entry in the FIB for the route network prefix (referencing a FECTable entry that includes the EBNHI) to ensure that network packetsaddressed towards the route network prefix could be directed to theroute network prefix when necessary. That is, there is an existing FIBentry in the FIB associated with the route network prefix. However,because the PBNHI now matches the NBNHI, and because the FIB is limitedor compressed to include FIB entries corresponding to routes associatedwith a set of the least specific network prefixes in the RIB, the FIBentry associated with the parent network prefix (which is the leastspecific network prefix between the parent network prefix and the routenetwork prefix) is retained over the existing FIB entry associated withthe route network prefix.

On the other hand, further to Step 640, if it is determined that thePBNHI does not match the NBNHI, the process proceeds to Step 686 (seee.g., FIG. 6F). In one embodiment of the invention, the PBNHI notmatching the NBNHI, while also not matching the EBNHI (see e.g., Step620), may be indicative that, as mentioned above, prior to the update ofthe route corresponding to the route network prefix, the difference inBNHI amongst the parent network prefix and the route network prefixwould have warranted creation of a FIB entry in the FIB for the routenetwork prefix (referencing a FEC Table entry that includes the EBNHI)to ensure that network packets addressed towards the route networkprefix could be directed to the route network prefix when necessary.That is, as it stands, there is an existing FIB entry in the FIBassociated with the route network prefix. However, because the PBNHIalso does not match the NBNHI, the existing FIB entry in the FIBassociated with the route network prefix must be updated to include aFEC index that references an existing (or new) FEC Table entry in theFEC Table that includes the NBNHI (in place of the existing FEC indexthat references an existing FEC Table entry in the FEC Table thatincludes the EBNHI).

Proceeding with FIG. 6C, in Step 642, after determining (in Step 640)that the PBNHI does match the NBNHI, the existing FIB entry in the FIBassociated with the route network prefix is identified. In oneembodiment of the invention, identification of the existing FIB entryassociated with the route network prefix may entail comparing the routenetwork prefix with each network prefix specified in each existing FIBentry in the FIB. Subsequently, the existing FIB entry in the FIB thatspecifies a network prefix matching the route network prefix may beselected as the existing FIB entry in the FIB associated with the routenetwork prefix. Subsequently, in Step 644, the existing FIB entry in theFIB associated with the route network prefix (identified in Step 642) isdeleted/removed from the FIB.

In Step 646, any children of the route network prefix are identified, ifany. In one embodiment of the invention, proceeding onwards to Step 646may have followed: (i) the creation of a new FIB entry associated withthe route network prefix in a first case (see e.g., Step 628); (ii) thedeletion/removal of an existing FIB entry associated with the routenetwork prefix in a second case (see e.g., Step 644); or (iii) theupdating of an existing FIB entry associated with the route networkprefix in a third case (see e.g., Step 692). Nevertheless, in oneembodiment of the invention, identification of the children may involveaccessing the trie nodal information associated with the route networkprefix and obtaining the set of child references, if any, specified inthe route trie nodal information.

In Step 648, a fourth determination is made as to whether any childrenwere identified in Step 646. If it is determined that zero children wereidentified (e.g., the set of child references specified in the routetrie nodal information referenced NULL memory space), then the processends. On the other hand, if it is determined that at least one child (ofthe route network prefix) has been identified, then the process proceedsto Step 660 (see e.g., FIG. 6D).

Turning to FIG. 6D, in Step 660, after determining (in Step 648) that atleast one child (of the route network prefix) had been identified, childbridging next hop information (CBNHI) for the/each child of the routenetwork prefix is obtained. In one embodiment of the invention,obtaining of the CBNHI may involve accessing the trie nodal informationassociated with a/the child node (or network prefix) identified in Step646 (see e.g., FIG. 6C) (using a/the child reference specified in theroute trie nodal information) and obtaining the corresponding BNHI(e.g., value) specified in a/the child trie nodal information.

In Step 662, a fifth determination is made as to whether the CBNHI(obtained in Step 660) matches the EBNHI (obtained in Step 606). If itis determined that the CBNHI does match the EBNHI, the process proceedsto Step 680 (see e.g., FIG. 6E). In one embodiment of the invention, theCBNHI matching the EBNHI may be indicative that, as the route networkprefix is the least specific network prefix between the child networkprefix and the route network prefix, no FIB entry associated with thechild network prefix was warranted prior to the update to the existingroute in the RIB corresponding to the route network prefix. However, inview of the earlier occurrence of one of the three above-mentionedscenarios leading up to Step 646 (e.g., the creation of a new FIB entry,the deletion of an existing FIB entry, or the updating of an existingFIB entry, each/all associated with the route network prefix), creationof a new FIB entry respective to the child network prefix is required inorder to ensure that network packets addressed towards the child networkprefix (associated with CBNHI that matches the EBNHI) can be directed tothe child network prefix when necessary.

On the other hand, further to Step 662, if it is determined that theCBNHI does not match the EBNHI, the process proceeds to Step 664. In oneembodiment of the invention, the CBNHI not matching the EBNHI may beindicative that, prior to the update to the route detected in Step 600,the child network prefix is reachable through a first next hop (adjacentto the network element) that is different than a second next hop (alsoadjacent to the network element) through which the route network prefixwas reachable. That is, in one embodiment of the invention, the twodifferent BNHI (e.g., the CBNHI and the EBNHI) implies two different FECTable entries existing in the FEC Table, each including either the CBNHIor the EBNHI. Further, the first existing FEC Table entry including theCBNHI is referenced by a first existing FIB entry associated with thechild network prefix, whereas the second existing FEC Table entryincluding the EBNHI was referenced by a second existing (but nowpotentially deleted) FIB entry associated with the route network prefix.Therefore, summarily, at this point, there presently exists a FIB entry(referencing the CBNHI) in the FIB associated with the child networkprefix.

Proceeding with FIG. 6D, in Step 664, after determining (in Step 662)that the CBNHI does not match the EBNHI, a sixth determination is madeas to whether the CBNHI, instead, matches the NBNHI. If it is determinedthat the CBNHI does match the NBNHI, the process proceeds to Step 666.In one embodiment of the invention, the CBNHI matching the NBNHI may beindicative that both the child network prefix and the route networkprefix (now associated with the updated NBNHI) are reachable through thesame next hop (adjacent to the network element) along one or morepath(s) that includes at least the next hop. Further, as discussedabove, because the CBNHI, additionally, does not match the EBNHI (seee.g., Step 662), there presently exists a FIB entry (referencing theCBNHI) in the FIB associated with the child network prefix. However, inlight of the CBNHI now matching the NBNHI: (i) further to two of thethree above-mentioned scenarios leading to Step 646 (e.g., the creationof a new FIB entry, or the updating of an existing FIB entry, associatedwith the route network prefix) and because the FIB is limited orcompressed to include FIB entries corresponding to routes associatedwith a set of the least specific network prefixes in the RIB, theexisting FIB entry associated with the route network prefix (which isthe least specific network prefix between the child network prefix andthe route network prefix) is retained over the existing FIB entryassociated with the child network prefix; or (ii) further to theremainder of the three above-mentioned scenarios leading to Step 646(e.g., the deletion of an existing FIB entry associated with the routenetwork prefix) and because there exists a FIB entry in the FIBassociated with the child network prefix, no additional steps arerequired to ensure that network packets addressed to the child networkprefix can be directed to the child network prefix when necessary.

On the other hand, further to Step 664, if it is determined that theCBNHI does not match the NBNHI, the process ends. In one embodiment ofthe invention, the CBNHI not matching the NBNHI, while also not matchingthe EBNHI (see e.g., Step 662) may be indicative that the child networkprefix is already associated with an existing FIB entry in the FIB (as aresult of the CBNHI not matching the EBNHI). Further, in the CBNHI notmatching the NBNHI, the child network prefix would require a FIB entryin the FIB to ensure that network packets addressed to the child networkprefix can be directed to the child network prefix when necessary.However, as mentioned earlier, because the child network prefix isalready associated with an existing FIB entry, no further actions arerequired in this case.

In Step 666, after determining (in Step 664) that the CBNHI does matchthe NBNHI, a seventh determination is made as to whether there exists aFIB entry in the FIB associated with the route network prefix. In oneembodiment of the invention, recall that further to one possiblescenario leading up to this point, the FIB entry in the FIB associatedwith the route network prefix may have been deleted (see e.g., Step644). Accordingly, Step 666 serves as check to account for thatscenario. In one embodiment of the invention, determining whether thereexists a FIB entry associated with the route network prefix may entailcomparing the route network prefix with each network prefix specified ineach existing FIB entry in the FIB. Subsequently, if the comparisonproduces a result, then a FIB entry associated with the route networkprefix does exist; otherwise, there is no existing FIB entry in the FIBassociated with the route network prefix.

Further to Step 666, if it is determined that there is an existing FIBentry in the FIB associated with the route network prefix, the processproceeds to Step 668. In one embodiment of the invention, because theCBNHI does not match the EBNHI (see e.g., Step 662), there is anexisting FIB entry in the FIB associated with the child network prefix.In addition, because the CBNHI does match the NBNHI, because there is anexisting FIB entry in the FIB associated with the route network prefix,and because, in one embodiment of the invention, the FIB is limited orcompressed to include FIB entries corresponding to routes associatedwith a set of the least specific network prefixes in the RIB, theexisting FIB entry associated with the route network prefix (which isthe least specific network prefix between the child network prefix andthe route network prefix) is retained over the existing FIB entryassociated with the child network prefix.

On the other hand, further to Step 666, if it is determined that the FIBdoes not contain a FIB entry associated with the route network prefix,the process ends. In one embodiment of the invention, from the abovediscussion leading to this step, the child network prefix maintains anassociated FIB entry in the FIB because the CBNHI does not match theEBNHI (see e.g., Step 662). Further, with the CBNHI instead matching theNBNHI (see e.g., Step 664) and with no existing FIB entry associatedwith the route network prefix in the FIB, the existing FIB entryassociated with the child network prefix requires retaining in order toensure that network packets addressed to the child network prefix can bedirected to the child network prefix. Conclusively, no further actionsare needed and the process thus ends.

Proceeding with FIG. 6D, in Step 668, after determining (in Step 666)that there does exist a FIB entry associated with the route networkprefix in the FIB, the existing FIB entry associated with the childnetwork prefix is identified. In one embodiment of the invention,identification of the existing FIB entry associated with the childnetwork prefix may entail comparing the child network prefix with eachnetwork prefix specified in each existing FIB entry in the FIB.Subsequently, the existing FIB entry in the FIB that specifies a networkprefix matching the child network prefix may be selected as the existingFIB entry in the FIB associated with the child network prefix. Followingthis, in Step 670, the existing FIB entry associated with the childnetwork prefix (identified in Step 670) is removed/deleted from the FIBon the network element. Subsequently, the process ends.

Turning to FIG. 6E, in Step 680, after determining (in Step 662) thatthe CBNHI does match the EBNHI, the FEC Table entry in the FEC Tablethat includes the EBNHI is identified. In one embodiment of theinvention, identification of the existing FEC Table entry including theEBNHI may entail comparing the EBNHI with each BNHI specified in eachexisting FEC Table entry in the FEC Table. Subsequently, the existingFEC Table entry in the FEC Table that specifies BNHI matching the EBNHImay be selected as the existing FEC Table entry in the FEC Table thatincludes the EBNHI.

In Step 682, the FEC index specified in the FEC Table entry (identifiedin Step 680) is obtained. In Step 684, a new FIB entry for the childnetwork prefix is created in the FIB on the network element. In oneembodiment of the invention, the new FIB entry (for the child networkprefix) may include the child network prefix and the FEC index obtainedin Step 682. Subsequently, the process ends.

Turning to FIG. 6F, in Step 686, after determining (in Step 640) thatthe PBNHI does not match the NBNHI, a search for a FEC Table entry thatincludes the NBNHI is attempted. In one embodiment of the invention,searching for a FEC Table entry that includes the NBNHI may entailcomparing the NBNHI with each BNHI specified in each existing FEC Tableentry in the FEC Table. Subsequently, if the comparison produces aresult, then a FEC Table entry that includes the NBNHI does exist;otherwise, there is no existing FEC Table entry in the FEC Table thatincludes the NBNHI.

In Step 688, an eight determination is made as to whether an existingFEC Table entry was identified as a result of the search performed inStep 686. If it is determined that an existing FEC Table entry wasindeed identified, then the process proceeds to Step 690. Following thisdeduction, in Step 690, the FEC index specified in the existing FECTable entry (identified in Step 686) is obtained.

On the other hand, further to Step 688, if it is determined that noexisting FEC Table entry was identified during Step 686, then theprocess proceeds to Step 694. Following this deduction, in Step 694, anew FEC Table entry is created. In one embodiment of the invention, thenew FEC Table entry may include a new FEC index (identifying the new FECTable entry) and the NBNHI.

In Step 692, following the obtaining of a FEC index specified in anexisting FEC Table entry (see e.g., Step 690) or the creation of a newFEC Table entry including a new FEC index (see e.g., Step 694), theexisting FIB entry for the route network prefix is updated. In oneembodiment of the invention, the existing FIB entry (for the routenetwork prefix) may be updated to include the obtained FEC index (ofStep 690) that references the aforementioned existing FEC Table entry.In another embodiment of the invention, the existing FIB entry (for theroute network prefix) may be updated to include the new FEC index thatreferences the created/populated FEC Table entry (for the route networkprefix) in Step 694. In one embodiment of the invention, the objectiveof the update may be to replace an existing FEC index (referencing anexisting FEC Table entry that includes the EBNHI) specified in theexisting FIB entry (for the route network prefix) with a FEC indexreferencing a FEC Table entry that includes the NBNHI. From here, theprocess proceeds to Step 646.

FIGS. 7A-7D show various aspects of an example in accordance with one ormore embodiments of the invention. The following example is forexplanatory purposes only and not intended to limit the scope of theinvention.

With respect to the following example, consider a first scenario whereinthe RIB on a network element has just been updated with the addition ofa new route. The new route may correspond to the network prefix“10.0.1.0/16”. Prior to embodiments of the invention, the addition ofthe new route in the RIB may trigger programming of the FIB on thenetwork element to include a new FIB entry for the new route. The FIB isprogrammed regardless of whether the new route is subsumed by a lesserspecific route in the FIB, thereby maintaining a one-to-onecorrespondence between entries in the FIB and entries in the RIB.

In contrast, in detecting the addition of the new route in the RIB,embodiments of the invention subsequently pursue the addition of theroute network prefix (associated with the new route) to the NPT on thenetwork element. Turning to FIG. 7A, the addition of the route networkprefix may position the route network prefix P₃ (708) below an existingnetwork prefix P₁ (704) in the NPT (700). In one embodiment of theinvention, the position of the route network prefix P₃ (708) under theexisting network prefix P₁ (704) may be indicative that the formerprefix may include a first set of available IP addresses that are asubset of a second set of IP addresses available through latter prefix.Based on the location of the route network prefix P₃ (708) in the NPT(700), the existing network prefix P₁ (704) is identified as the parentnetwork prefix for the route network prefix P₃ (708).

After obtaining route bridging next hop information (RBNHI) and parentbridging next hop information (PBNHI) for the route network prefix andthe parent network prefix, respectively, a comparison of the RBNHI andthe PBNHI is performed. The result, in one embodiment of the invention,may be that the RBNHI matches the PBNHI. Subsequently, the updating ofthe FIB to include a new FIB entry for the added route (as performed inaccordance with conventional network element operation) is waivedbecause the existing FIB entry associated with the parent network prefixP₁ (704) references the bridging next hop information (BNHI) (e.g.,PBNHI, which matches the RBNHI) necessary to direct network packetstowards both the parent network prefix P₁ (704) and the route networkprefix P₃ (708). In waiving the updating of the FIB, the FIB iscompressed to include at least one fewer entry relative to the RIB. FIG.7B shows a comparison between a first FIB (720A) (in accordance withconventional network element operation) and a second FIB (720B) (inaccordance with embodiments of the invention) respective to the firstscenario entailing the addition of a new route to the RIB.

Further to the example, consider a second scenario wherein the RIB hasjust been updated with a modification to an existing route. The existingroute may correspond to the network prefix “12.0.2.0/16”. Further, themodification to the existing route may entail the use of a differentnext hop due to, for example, the failure of the original next hop.Prior to embodiments of the invention, the modification of the existingroute in the RIB may trigger programming of the FIB to update theexisting FIB entry associated with the route network prefix to replacean original FEC index (referencing BNHI for the original next hop) withanother (existing or new) FEC index (referencing BNHI for the differentnext hop). Summarily, a modification to an existing route, subject toconventional network element operation, may not entail much more thanthe change of data (e.g., FEC indices) within the FIB.

In contrast, in detecting the update to the existing route in the RIB,embodiments of the invention may first locate an existing network prefixassociated with the existing route in the NPT. Returning to FIG. 7A, theNPT (700) may show the route network prefix P₄ (710) to be positionedbetween additional existing network prefixes P₂ (706) and P₅ (712).Based on the located position of the route network prefix P₄ (710) inthe NPT (700), the existing network prefix P₂ (706) is identified as theparent network prefix, whereas the existing network prefix P₅ (712) isidentified as the child network prefix, for the route network prefix P₄(710).

After obtaining the existing bridging next hop information (EBNHI) andthe new bridging next hop information (NBNHI) for the route networkprefix P₄ (710) prior to and after the update, respectively, as well asthe PBNHI for the parent network prefix P₂ (706), a first comparisonensues between the PBNHI and the EBNHI. The result of the firstcomparison, in one embodiment of the invention, may be that the PBNHIdoes not match the EBNHI, indicating that, prior to the update, theparent network prefix P₂ (706) and the route network prefix P₄ (710) didnot share a common next hop. This initial mismatching would haverequired the route network prefix P₄ (710) to be associated with a FIBentry of its own, separate from the existing FIB entry associated withthe parent network prefix P₂ (706), prior to the update. Subsequent tothe first comparison, a second comparison is thus performed between thePBNHI and the NBNHI. The result of the second comparison, in oneembodiment of the invention, may deduce that the PBNHI matches theNBNHI, indicating that, after the update (or currently), the parentnetwork prefix P₂ (706) and the route network prefix P₄ (710) now sharea common next hop. In view of this matching, the existing FIB entryassociated with the route network prefix P₄ (710) is removed, furthercompressing the FIB, because the existing FIB entry associated with theparent network prefix P₂ (706) retains the BNHI (e.g., PBNHI, whichmatches the NBNHI) necessary to direct network packets towards both theparent network prefix P₂ (706) and the route network prefix P₄ (710).FIG. 7C shows a comparison between the first FIB (720A) (in accordancewith conventional network element operation) and the second FIB (720B)(in accordance with embodiments of the invention) respective to thefirst scenario and a portion of the second scenario entailing the updateof a new route in the RIB.

Continuing with the second scenario, a child bridging next hopinformation (CBNHI) associated for the child network prefix P₅ (712) maybe obtained. Subsequently, a third comparison is performed between theCBNHI and the EBNHI, which, in one embodiment of the invention, mayresult in a determination that the CBNHI does not match the EBNHI. Thismismatching may be indicative that, prior to the update, the childnetwork prefix P₅ (712) and the route network prefix P₄ (710) did notshare a common next hop. Consequently, the child network prefix P₅ (712)would have required its own FIB entry, separate from the existing FIBentry associated with the route network prefix P₄ (710), prior to theupdate. Further, based on this first determination, a fourth comparisonmay be performed between the CBNHI and the NBNHI. The result of thefourth comparison, in one embodiment of the invention, may be that theCBNHI matches the NBNHI, thus indicating that, after the update (orcurrently), the child network prefix P₅ (712) shares a common next hopwith the route network prefix P₄ (710). In view of this matching,because the existing FIB entry associated with the child network prefixP₅ (712) is removed, even further compressing the FIB, because theexisting FIB entry associated with the parent network prefix P₂ (706)retains the BNHI (e.g., PBNHI, which matches the NBNHI, which matchesthe CBNHI) necessary to direct network packets towards the parentnetwork prefix P₂ (706), the route network prefix P₄ (710), and further,the child network prefix P₅ (712). FIG. 7D shows a comparison betweenthe first FIB (720A) (in accordance with conventional network elementoperation) and the second FIB (720B) (in accordance with embodiments ofthe invention) respective to the remainder of the second scenarioentailing the update of a new route in the RIB.

Embodiments of the invention may be implemented on a computing system.Any combination of mobile, desktop, server, router, switch, embeddeddevice, or other types of hardware may be used. For example, as shown inFIG. 8A, the computing system (800) may include one or more computerprocessors (802), non-persistent storage (804) (e.g., volatile memory,such as random access memory (RAM), cache memory), persistent storage(806) (e.g., a hard disk, an optical drive such as a compact disk (CD)drive or digital versatile disk (DVD) drive, a flash memory, etc.), acommunication interface (812) (e.g., Bluetooth interface, infraredinterface, network interface, optical interface, etc.), and numerousother elements and functionalities.

The computer processor(s) (802) may be an integrated circuit forprocessing instructions. For example, the computer processor(s) may beone or more cores or micro-cores of a processor. The computing system(800) may also include one or more input devices (810), such as atouchscreen, keyboard, mouse, microphone, touchpad, electronic pen, orany other type of input device.

The communication interface (812) may include an integrated circuit forconnecting the computing system (800) to a network (not shown) (e.g., alocal area network (LAN), a wide area network (WAN) such as theInternet, mobile network, or any other type of network) and/or toanother device, such as another computing device.

Further, the computing system (800) may include one or more outputdevices (808), such as a screen (e.g., a liquid crystal display (LCD), aplasma display, touchscreen, cathode ray tube (CRT) monitor, projector,or other display device), a printer, external storage, or any otheroutput device. One or more of the output devices may be the same ordifferent from the input device(s). The input and output device(s) maybe locally or remotely connected to the computer processor(s) (802),non-persistent storage (804), and persistent storage (806). Manydifferent types of computing systems exist, and the aforementioned inputand output device(s) may take other forms.

Software instructions in the form of computer readable program code toperform embodiments of the invention may be stored, in whole or in part,temporarily or permanently, on a non-transitory computer readable mediumsuch as a CD, DVD, storage device, a diskette, a tape, flash memory,physical memory, or any other computer readable storage medium.Specifically, the software instructions may correspond to computerreadable program code that, when executed by a processor(s), isconfigured to perform one or more embodiments of the invention.

The computing system (800) in FIG. 8A may be connected to or be a partof a network. For example, as shown in FIG. 8B, the network (820) mayinclude multiple nodes (e.g., node X (822), node Y (824)). Each node maycorrespond to a computing system, such as the computing system shown inFIG. 8A, or a group of nodes combined may correspond to the computingsystem shown in FIG. 8A. By way of an example, embodiments of theinvention may be implemented on a node of a distributed system that isconnected to other nodes. By way of another example, embodiments of theinvention may be implemented on a distributed computing system havingmultiple nodes, where each portion of the invention may be located on adifferent node within the distributed computing system. Further, one ormore elements of the aforementioned computing system (800) may belocated at a remote location and connected to the other elements over anetwork.

Although not shown in FIG. 8B, the node may correspond to a blade in aserver chassis that is connected to other nodes via a backplane. By wayof another example, the node may correspond to a server in a datacenter. By way of another example, the node may correspond to a computerprocessor or micro-core of a computer processor with shared memoryand/or resources.

The nodes (e.g., node X (822), node Y (824)) in the network (820) may beconfigured to provide services for a client device (826). For example,the nodes may be part of a cloud computing system. The nodes may includefunctionality to receive requests from the client device (826) andtransmit responses to the client device (826). The client device (826)may be a computing system, such as the computing system shown in FIG.8A. Further, the client device (826) may include and/or perform all or aportion of one or more embodiments of the invention.

The computing system or group of computing systems described in FIGS. 8Aand 8B may include functionality to perform a variety of operationsdisclosed herein. For example, the computing system(s) may performcommunication between processes on the same or different system. Avariety of mechanisms, employing some form of active or passivecommunication, may facilitate the exchange of data between processes onthe same device. Examples representative of these inter-processcommunications include, but are not limited to, the implementation of afile, a signal, a socket, a message queue, a pipeline, a semaphore,shared memory, message passing, and a memory-mapped file. Furtherdetails pertaining to a couple of these non-limiting examples areprovided below.

The above description of functions presents only a few examples offunctions performed by the computing system of FIG. 8A and the nodesand/or client device in FIG. 8B. Other functions may be performed usingone or more embodiments of the invention.

While the invention has been described with respect to a limited numberof embodiments, those skilled in the art, having benefit of thisdisclosure, will appreciate that other embodiments can be devised whichdo not depart from the scope of the invention as disclosed herein.Accordingly, the scope of the invention should be limited only by theattached claims.

What is claimed is:
 1. A method for programming a network element,comprising: detecting an update to a first route in a routinginformation base (RIB) and locating a first route network prefixassociated with the first route; determining that, prior to the update,a first parent network prefix and the first route network prefix werereachable using a pair of different next hops connected to the networkelement; determining that, after the update, the first parent networkprefix and the first route network prefix are reachable using a firstcommon next hop connected to the network element; and in response to thedetermination that the first parent network prefix and the first routenetwork prefix are reachable using the first common next hop after theupdate, removing an existing forwarding information base (FIB) entry inthe FIB associated with the first route network prefix.
 2. The method ofclaim 1, wherein determining that the first parent network prefix andthe first route network prefix were reachable using the pair ofdifferent next hops connected to the network element comprises:obtaining existing bridging next hop information (EBNHI) correspondingto the first route network prefix prior to the update; obtaining parentbridging next hop information (PBNHI) corresponding to the first parentnetwork prefix; and determining that the EBNHI does not match the PBNHI,wherein the EBNHI is associated with one of the next hops of the pair ofdifferent next hops, and wherein the PBNHI is associated with the othernext hop of the first pair of different next hops.
 3. The method ofclaim 1, wherein determining that the first parent network prefix andthe first route network prefix are reachable using the first common nexthop connected to the network element comprises: obtaining new bridgingnext hop information (NBNHI) corresponding to the first route networkprefix after the update; and determining that the NBNHI matches thePBNHI, wherein the NBNHI is associated with the first common next hop,and wherein the first common next hop is one of the first pair ofdifferent next hops.
 4. The method of claim 1, further comprising:identifying, based on the locating, a child network prefix for the firstroute network prefix using a network prefix trie (NPT); determiningthat, prior to the update, the child network prefix and the first routenetwork prefix were reachable using a second pair of different next hopsconnected to the network element; determining that, after the update,the child network prefix and the first route network prefix arereachable using a second common next hop connected to the networkelement; and removing a second existing FIB entry in the FIB associatedwith the child network prefix.
 5. The method of claim 4, whereinidentifying the child network prefix comprises: accessing trie nodalinformation associated with the first route network prefix; obtaining achild reference from the trie nodal information; and identifying thechild network prefix using the child reference.
 6. The method of claim1, further comprising: detecting that a second route is removed from theRIB on the network element; identifying a second route network prefixassociated with the second route; obtaining route bridging next hopinformation (RBNHI) corresponding to the second route network prefix;identifying a second parent network prefix for the second route networkprefix; obtaining a second PBNHI corresponding to the second parentnetwork prefix; determining that the RBNHI does not match the secondPBNHI; removing a third existing FIB entry in the FIB associated withthe second route network prefix.
 7. The method of claim 6, furthercomprising: identifying, based on the locating, a second child networkprefix for the first route network prefix using the NPT; obtaining childbridging next hop information (CBNHI) associated with the second childnetwork prefix; based on a determination that the CBNHI matches thesecond PBNHI and the CBNHI does not match the RBNHI, removing a fourthexisting FIB entry in the FIB associated with the second child networkprefix.
 8. The method of claim 1, wherein determining the first parentnetwork prefix comprises: accessing trie nodal information associatedwith the first route network prefix; obtaining a parent reference fromthe trie nodal information; and identifying the first parent networkprefix using the parent reference.
 9. The method of claim 8, wherein thetrie nodal information comprises bridging next hop information (BNHI)corresponding to the first route network prefix and the parentreference.
 10. The method of claim 9, wherein the trie nodal informationfurther comprises at least one child reference.
 11. A network element,comprising: a processor; a data plane comprising a forwardinginformation base (FIB); and a control plane comprising a routinginformation base (RIB) and a FIB Compressor operatively connected to theRIB and the FIB, and when the FIB Compressor executes on the processor,the FIB Compressor performs a method, the method comprises: detecting anupdate to a first route in a routing information base (RIB) and locatinga first route network prefix associated with the first route;determining that, prior to the update, a first parent network prefix andthe first route network prefix were reachable using a pair of differentnext hops connected to the network element; determining that, after theupdate, the first parent network prefix and the first route networkprefix are reachable using a first common next hop connected to thenetwork element; and in response to the determination that the firstparent network prefix and the first route network prefix are reachableusing the first common next hop after the update removing an existingforwarding information base (FIB) entry in the FIB associated with thefirst route network prefix.
 12. The network element of claim 11, whereindetermining that the first parent network prefix and the first routenetwork prefix were reachable using the pair of different next hopsconnected to the network element comprises: obtaining existing bridgingnext hop information (EBNHI) corresponding to the first route networkprefix prior to the update; obtaining parent bridging next hopinformation (PBNHI) corresponding to the first parent network prefix;and determining that the EBNHI does not match the PBNHI, wherein theEBNHI is associated with one of the next hop of the pair of differentnext hops, and wherein the PBNHI is associated with the other next hopof the first pair of different next hops.
 13. The network element ofclaim 11, wherein determining that the first parent network prefix andthe first route network prefix are reachable using the first common nexthop connected to the network element comprises: obtaining new bridgingnext hop information (NBNHI) corresponding to the first route networkprefix after the update; and determining that the NBNHI matches thePBNHI, wherein the NBNHI is associated with the first common next hop,and wherein the first common next hop is one of the first pair ofdifferent next hops.
 14. The network element of claim 11, furthercomprising: identifying, based on the locating, a child network prefixfor the first route network prefix using a network prefix trie (NPT);determining that, prior to the update, the child network prefix and thefirst route network prefix were reachable using a second pair ofdifferent next hops connected to the network element; determining that,after the update, the child network prefix and the first route networkprefix are reachable using a second common next hop connected to thenetwork element; and removing a second existing FIB entry in the FIBassociated with the child network prefix.
 15. The network element ofclaim 14, wherein identifying the child network prefix comprises:accessing trie nodal information associated with the first route networkprefix; obtaining a child reference from the trie nodal information; andidentifying the child network prefix using the child reference.
 16. Thenetwork element of claim 11, further comprising: detecting that a secondroute is removed from the RIB on the network element; identifying asecond route network prefix associated with the second route; obtainingroute bridging next hop information (RBNHI) corresponding to the secondroute network prefix; identifying a second parent network prefix for thesecond route network prefix; obtaining a second PBNHI corresponding tothe second parent network prefix; determining that the RBNHI does notmatch the second PBNHI; removing a third existing FIB entry in the FIBassociated with the second route network prefix.
 17. The network elementof claim 16, further comprising: identifying, based on the locating, asecond child network prefix for the first route network prefix using theNPT; obtaining child bridging next hop information (CBNHI) associatedwith the second child network prefix; based on a determination that theCBNHI matches the second PBNHI and the CBNHI does not match the RBNHI,removing a fourth existing FIB entry in the FIB associated with thesecond child network prefix.
 18. The network element of claim 11,wherein determining the first parent network prefix comprises: accessingtrie nodal information associated with the first route network prefix;obtaining a parent reference from the trie nodal information; andidentifying the first parent network prefix using the parent reference.19. The network element of claim 18, wherein the trie nodal informationcomprises bridging next hop information (BNHI) corresponding to thefirst route network prefix and the parent reference.
 20. The networkelement of claim 19, wherein the trie nodal information furthercomprises at least one child reference.